Unable to refresh access tokens after it expires

#1

Hey, we are unable to refresh any integration with an updated access token once it expires after 30 days.

All of the access tokens can be refreshed before 30 days but not after it expires. In the logs, we can see we get a response from the server

{
  error: 'invalid_grant',
  error_description: 'Invalid or unknown refresh token provided.'
}

which doesn’t make any sense because the refresh token is valid for more than 200 days or are we missing something that isn’t mentioned in the doc?

Currently, all of our PagerDuty integrations are failing after 30 days and we have no clue how to resolve it. I believe there is some missing that hasn’t been communicated properly, already tried reaching out to support but they hardly respond to tickets I believe.

#2

We met this problem too. No clue found in our server side. Any supportor can help? We can’t get access through refresh token too after 30 days. We are classical Oauth client. Do you have any updates?@ Nadeem

#3

+1 – We’re seeing the exact same issue. Once our access token expires we aren’t able to refresh it.

#4

I’ve contact with their support, it has been fixed now for new token. So for new-create token, it will works correctly now.

#5

Yes, we received the reply from support as well, but haven’t been able to refresh any existing tokens. Have you verified with existing tokens? or will it work for a new token after authentication?

PagerDuty support is slow and abstracted we are hesitant if it will work or not after asking all the users to reintegrate

#6

Hi folks,

I checked internally and can confirm that new refresh settings only take effect after re-authorizing the app.

As @ray.li.1 and @nadeem.siddique mentioned in the comments, fix is in place for all fresh authorizations moving forward.